Accessible Installer Wizard Readme

Getting started

Accessible Installer Wizard provides a graphical interface for building installer projects without requiring you to manually write Inno Setup scripts. You can create a new installer using the guided setup wizard, build a project manually, or import an existing Inno Setup script.

The quickest way to create an installer is with the setup wizard.

Open Accessible Installer Wizard.
Choose New with setup wizard from the File menu.
Enter the basic information about your application.
Select the files or folder that should be included.
Choose the installer options you require.
Finish the wizard.
Review or change the generated project if required.
Compile the project to create your installer.

You can also create an empty project if you prefer to configure everything yourself.

Tutorial: build your first installer

This tutorial creates a simple installer for an application that already exists in a folder on your computer.

Before you begin, put the files for your application together in one folder. The folder should contain the main .exe file and anything else the application needs.

1. Start the guided setup wizard

Open Accessible Installer Wizard.
Choose File, then New with setup wizard.
The first page asks for information about your application.

2. Enter the application details

Enter the Application name. For this tutorial, you could enter My First Application.
Enter the Application version, for example 1.0.
Enter the publisher name if required.
Enter the publisher website if required.
Move to the next page.

Only the application name is required on this page. The other information is useful for a finished installer but can be left blank while experimenting.

3. Choose the application files

Use Browse beside Application folder.
Select the folder containing your application.
Choose the main executable if it has not been selected automatically.
Leave Include all subfolders selected if your application uses folders inside its main folder.
Move to the next page.

The application folder becomes the source for the installer. Its contents will normally be installed into the application's installation folder.

4. Choose how the application is installed

Choose whether the application should be available to everyone on the computer or only the current user.
Choose the Windows architecture supported by the application.
Review the installation folder.
Move to the next page.

For a normal 64-bit application, 64-bit Windows is usually the appropriate architecture choice. If your application supports both 32-bit and 64-bit Windows, choose that option instead.

5. Choose shortcuts and launch options

Leave Create a Start menu shortcut selected if you want the application added to the Start menu.
Select Offer a desktop shortcut if the person installing the application should be able to choose a desktop shortcut.
Select Offer to launch after installation if Setup should offer to start the application when installation finishes.
Move to the final page.

6. Optional: add signing or installer sounds

You can skip this step for your first test installer.

If you have a code-signing certificate, open the Signing settings after completing the wizard and configure signing for the installer, uninstaller or individual application files.
If you want an audible cue when Setup opens or finishes, choose WAV files for the installer launch and installation complete sounds under Appearance.

7. Review the project

The final wizard page gives you a summary of the choices you made.

Read through the summary.
Go back if something needs changing.
Choose Finish when the information is correct.

8. Validate the installer

After the wizard closes, the project opens in the main window.

Press F7 to validate the project.
If no problems are reported, continue to the next step.
If validation reports a problem, correct it and press F7 again.

You can use Control+F9 to jump to the first validation issue, Control+F10 for the next issue, and Control+Shift+F10 for the previous issue.

9. Save the project

Press Control+S.
Choose where the project should be saved.

Saving the project lets you reopen it later when you need to build another version of the installer.

10. Compile the installer

Press Control+B to compile.
The compilation progress window is displayed while the installer is being built.
Compiler messages are also written to the Build log.
When compilation succeeds, the finished installer is placed in the configured output location.

11. If the build fails

Do not panic. The compiler normally tells you where the problem is.

Press F8 to jump to the first compiler error.
Press F9 for the next compiler error.
Press Shift+F9 for the previous compiler error.
Read the Build log for the full compiler output.

12. Test the finished installer

Run the installer you created and check the basics:

The application installs into the expected folder.
The application starts.
The expected Start menu or desktop shortcuts are created.
Any files and subfolders required by the application are present.
The application can be uninstalled successfully.

That is enough for your first installer. Once the basic build works, you can return to the project and add tasks, components, registry entries, script constants and other advanced options as required.

The main window

The main window contains categories for the different parts of your installer.

Move through the categories and enter the information required for your project.

You do not need to configure every available option. Many settings can be left at their defaults.

The available areas include application information, files, shortcuts, tasks, components, registry entries, installation types, cleanup entries, advanced settings and build options.

Application information

The main application settings describe the program you are packaging.

Application name.
Application version.
Publisher.
Application ID.
Default installation folder.
Default Start menu group.
Supported architectures.
64-bit installation mode.
Minimum Windows version.

The Application ID uniquely identifies your application to Windows and the installer. Accessible Installer Wizard can generate an ID for you.

Adding files

The Files section controls which files are installed.

When adding an entry, choose either a file or a folder.

If you choose a folder, Accessible Installer Wizard automatically configures the source so that the contents of the folder are included.

You can also choose whether subfolders should be included.

The destination controls where the files are placed on the user's computer. Inno Setup constants such as {app} can be used to refer to standard locations.

For most application files, {app} means the folder where the user chooses to install your application.

Portable source paths

When an Inno Setup script is generated or compiled, Accessible Installer Wizard prefers relative source paths for files that are inside the project or generated script folder. This makes it easier to move a complete installer project to another folder or computer without rewriting every source path.

Files outside the project folder may remain as absolute paths because there is no safe relative location for them. If you intend to move a project between computers, keep required application files and installer support files together with the project where practical.

Signing an installed file

Each Files entry can optionally request code signing.

Do not sign leaves the file unchanged.
Sign file signs the source file using the configured signing tool.
Sign only if unsigned signs the file only when it is not already signed.

File signing requires code signing to be configured for the project. See Code signing.

Code signing

Accessible Installer Wizard can use Inno Setup's signing support to digitally sign the generated installer, the generated uninstaller and individual application files.

The Signing settings include:

Digitally sign generated installer EXE Signs the installer produced by the compiler.
Digitally sign uninstaller EXE Signs the uninstaller created for the installed application.
Signing tool name The name used by Inno Setup for the configured signing command. New projects use MSSIGN by default.
Signing tool command The command used to sign a file.

New projects provide a basic SHA-256 SignTool command:

signtool.exe sign /a /fd SHA256 $f

The $f value is replaced with the file being signed.

The default command does not choose a particular certificate provider or timestamp service. Configure the signing command for the certificate and timestamp service you use before making a public release.

Signing individual EXE or DLL files

Open the relevant entry in the Files section and use its Code signing choice. This is useful when the application EXE or DLLs should be signed as part of the installer build.

Sign only if unsigned is useful for projects containing a mixture of files that may already have valid signatures.

Code signing requires an appropriate code-signing certificate and signing tool. Enabling signing in Accessible Installer Wizard does not provide a certificate.

Installer sounds

Accessible Installer Wizard can include optional sounds that play during the installation experience.

Installer launch sound Plays when the installer window opens.
Installation complete sound Plays when installation succeeds and Setup reaches the Finished page.

Installer sounds currently use WAV files.

The selected sounds are embedded into the installer and extracted temporarily when required. The person running the installer does not need access to the original WAV file.

Sounds should be treated as additional feedback or decoration. Do not use a sound as the only way of communicating important installer information.

Shortcuts

The Shortcuts section creates shortcuts for installed programs or files.

When adding a shortcut you can specify:

Shortcut name The name displayed to the user.
Program or file to open The installed program, document or other file that the shortcut points to.
Create shortcut in Where the shortcut should appear, such as the Start menu or desktop.
Command-line arguments Optional information passed to the program when it starts.
Start in folder The working folder used when the program starts.
Shortcut icon file An optional custom icon.

Command-line arguments can normally be left blank unless the program you are installing requires them.

Tasks

Tasks are optional choices that can be presented to the user during installation.

For example, you could create a task allowing the user to choose whether a desktop shortcut should be created.

Shortcuts, files and other installer entries can then be associated with a task.

Components

Components allow an installer to contain optional parts of an application.

For example, an application could contain a main program, additional documentation and optional tools.

Components are useful when the user should be able to choose which parts of the application are installed.

Installation types

Installation types provide predefined installation configurations.

For example, an installer might offer:

Full.
Compact.
Custom.

Installation types are normally used with Components. They determine which components are selected for a particular type of installation.

If your installer does not need different installation configurations, you can usually leave this section alone.

Registry entries

The Registry section allows your installer to create or change Windows Registry values.

Only add registry entries when the application you are packaging requires them.

Be careful when editing registry settings. Incorrect registry changes can affect other applications or Windows itself.

Cleanup entries

Cleanup entries tell the installer to remove particular files or folders.

There are separate options for files that should be removed during installation and files that should be removed when the application is uninstalled.

These options are useful for removing temporary files, obsolete files from older versions, caches or folders that should not remain after uninstalling.

Flags and multiple choices

Many Inno Setup entries support flags.

Where known choices are available, Accessible Installer Wizard presents them as a list.

Use the Up and Down arrow keys to move through the list. Press Enter or Space to select or unselect the focused choice. More than one choice can be selected.

Advanced or unknown values can still be preserved when importing existing installer scripts.

Script constants

The Script constants section manages Inno Setup preprocessor #define values.

Constants are useful when the same information is required in several places.

For example, an application name or version can be stored once and then referenced elsewhere in the installer script.

Use Add to create a constant and Edit to change the selected constant.

Imported #define entries are automatically recognised and placed in this section where possible.

Script constants are different from compiler /D defines in the Build settings.

Importing an existing Inno Setup script

Accessible Installer Wizard can import existing .iss files.

Choose the import option and select the required script.

Recognised settings are converted into editable project information. Script content that the program does not directly manage is preserved where possible so that importing and exporting an installer does not unnecessarily discard advanced Inno Setup configuration.

After importing a script, review the project and use validation before compiling it.

Generating an Inno Setup script

Your project can be exported as an Inno Setup .iss script.

This is useful if you want to inspect the generated script, keep the script with a project, or edit it using another tool.

Importing and exporting is designed to preserve existing Inno Setup content wherever possible.

When possible, generated scripts use relative source paths rather than machine-specific absolute paths. Run entries that point to files included in the installer are also converted to their installed location, such as {app}\\Program.exe, where possible.

Validation

Before building an installer, Accessible Installer Wizard can check the project for common problems.

Validation can identify problems such as missing source files, invalid settings, malformed script constants and files configured for signing when project signing is not enabled.

If validation reports an error, select the error to move to the relevant part of the project where possible.

It is worth validating before every final build.

Building an installer

When the project is ready, use the Compile command to build it.

A progress window is displayed while compilation is taking place.

Compiler output is shown in the build log. If compilation fails, review the compiler errors for information about what needs to be corrected.

When compilation succeeds, the finished installer is placed in the configured output location.

Saving projects

Accessible Installer Wizard projects can be saved and reopened later.

Save your project if you expect to update the application or create another version of the installer in the future.

The project stores the information required by Accessible Installer Wizard and is separate from an exported .iss script or finished installer.

Keyboard shortcuts

Accessible Installer Wizard is designed to be usable without a mouse. The following table lists the program-specific keystrokes in the current version.

Shortcut	Action
`Control+N`	Create a new blank project.
`Control+O`	Open an existing project.
`Control+S`	Save the current project.
`Control+Shift+S`	Save the current project as a new file.
`Control+P`	Preview the generated Inno Setup script.
`Control+G`	Generate the Inno Setup `.iss` file.
`Control+B`	Compile the installer.
`F7`	Validate the project.
`F8`	Jump to the first detected compiler error.
`F9`	Jump to the next compiler error.
`Shift+F9`	Jump to the previous compiler error.
`Control+F8`	Open the project preflight report.
`Control+F9`	Jump to the first validation issue.
`Control+F10`	Jump to the next validation issue.
`Control+Shift+F10`	Jump to the previous validation issue.
`F1`	Show context-sensitive help for the control that currently has focus.
`Alt+F4`	Close Accessible Installer Wizard.

Moving around the main window

Tab and Shift+Tab move between controls.
In the Categories list, use Up and Down to choose a project area.
Pressing Tab from the Categories list moves directly into the first usable control on the current category page.
Shift+F10 opens the context menu for controls that provide one.

Flags and other multiple-choice lists

Flag lists are deliberately treated as one keyboard control rather than a row of individually tabbable checkboxes.

Key	Action
`Up` / `Down`	Move to the previous or next available choice.
`Home`	Move to the first choice.
`End`	Move to the last choice.
`Enter` or `Space`	Select or unselect the focused choice. Other selected choices remain selected.
`Tab`	Leave the list and move to the next control.
`Shift+Tab`	Leave the list and move to the previous control.

When you return to a multiple-choice list, the last focused item is retained where possible.

Script constants list

Key	Action
`Up` / `Down`	Move through script constants.
`Enter`	Edit the selected script constant.
`Delete`	Remove the selected script constant.

Standard Windows editing keys

Normal Windows editing and dialog keys also work where applicable. These include arrow keys in text fields, Control+C for copy, Control+X for cut, Control+V for paste, Control+A for select all, Enter to activate the default dialog action and Escape to cancel many dialogs.

If you are unsure what a field does, put focus on it and press F1. Context help is available for many of the more technical installer settings.

Inno Setup constants

Inno Setup uses constants to represent folders and other values.

You may see values such as:

{app} The application's installation folder.
{tmp} The installer's temporary folder.
{win} The Windows folder.
{sys} The Windows system folder.
{userappdata} The current user's application data folder.

Accessible Installer Wizard provides relevant constants through context menus in many fields.

You do not need to memorise them.

Advanced Inno Setup features

Accessible Installer Wizard aims to make common installer tasks straightforward without preventing more advanced use.

Some Inno Setup functionality may therefore remain visible as advanced values or preserved script content.

If you import a script containing something the program does not fully understand, it will attempt to preserve that information rather than silently remove it.

For complicated installers, it is always worth reviewing the generated .iss script before a final release.

Troubleshooting

My project says a source does not exist

Check that the original file or folder still exists.

If the project has been moved to another computer or folder, source paths may need to be updated.

Compilation fails

Read the build log and compiler errors.

Run project validation first, correct any reported problems and compile again.

A script constant is invalid

Open Script constants and edit the affected entry.

Pay particular attention to quotes in constant values and expressions.

My installed application is missing files from subfolders

Edit the relevant Files entry and make sure the option to include subfolders is enabled.

A file is not being signed

Make sure code signing is enabled in the Signing settings and that the signing tool command is correct for your certificate.

If only a particular application EXE or DLL should be signed, edit its Files entry and check the Code signing setting.

The signing command fails

Check that the signing tool is available and that the signing command matches your certificate setup. The default command is only a starting point and may need certificate or timestamp options for your environment.

A generated script contains an absolute path

Accessible Installer Wizard uses relative paths when the source can safely be expressed relative to the generated script. Files outside that project tree may remain absolute.

If the project needs to be portable, consider keeping its application payload and small support files together with the project.

An installer sound does not play

Check that the selected sound is a WAV file and that the source WAV still exists when the installer is compiled.

I imported an ISS file and something looks different

Accessible Installer Wizard may normalise some information while importing it.

Generate an .iss file and compare it with the original if the installer contains unusual or advanced Inno Setup configuration.

Custom or unsupported script content is preserved where possible.

About Inno Setup

Accessible Installer Wizard is an independent third-party front-end for Inno Setup.

Inno Setup is developed by Jordan Russell and Martijn Laan.

Accessible Installer Wizard is not affiliated with or endorsed by the Inno Setup developers.

The installers and scripts produced by Accessible Installer Wizard use Inno Setup technology. Users creating installers should ensure that their use of Inno Setup complies with its current licence and commercial-use terms.

Credits

Accessible Installer Wizard is a product of Nathan Tech.

Website. https://nathantech.net
Contact. https://nathantech.net/contact.php

Please provide any feedback, bug reports or accessibility suggestions.

We hope the program is useful.